Domain name control based social website account authentication

ABSTRACT

Methods of the present inventions allow for verifying the authenticity of social website accounts. An example embodiment of a domain name control based social website account authentication method may comprise the steps of receiving a request (that may include a business name and a business email address) to verify the authenticity of a social website account, determining whether the domain name used by the business email address is registered to and under control of the business, and—if so—certifying the authenticity of the social website account.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This patent application is related to U.S. patent application Ser. No.______ entitled: “Public Key Certificate Based Social Website AccountAuthentication” concurrently filed herewith and also assigned to The GoDaddy Group, Inc.

This patent application is related to U.S. patent application Ser. No.______ entitled: “Business Validation Based Social Website AccountAuthentication” concurrently filed herewith and also assigned to The GoDaddy Group, Inc.

FIELD OF THE INVENTION

The present inventions generally relate to social networking websitesand, more particularly, methods for verifying the authenticity of asocial website account.

SUMMARY OF THE INVENTION

An example embodiment of a domain name control based social websiteaccount authentication method may comprise the steps of receiving arequest (that may include a business name and a business email address)to verify the authenticity of a social website account, determiningwhether the domain name used by the business email address is registeredto and under control of the business, and—if so—certifying theauthenticity of the social website account.

An example embodiment of a public key certificate based social websiteaccount authentication method may comprise the steps of receiving arequest (that may include a business name and a business email address)to verify the authenticity of a social website account and determiningwhether a public key certificate has been issued for the domain nameused by the business email address. If a public key certificate has beenissued, the method may further comprise determining whether the publickey certificate identifies the business name and domain name provided inthe original request. If so, the method may further comprise determiningwhether the business email address is under the control of the businessand, if so, certifying the authenticity of the social website account.

An example embodiment of a business validation based social websiteaccount authentication method may comprise the steps of receiving arequest (that may include a business name and a business email address)to verify the authenticity of a social website account, validating thebusiness and business email address, and determining whether the domainname is registered to and under control of the business. If the businessand business email address are both validated, and the domain name isregistered to and under control of the business, the social websiteaccount's authenticity may be certified.

The features and advantages of the present inventions will be betterunderstood from the following detailed description taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 2 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 3 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 4 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 5 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 6 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 7 is a flow diagram illustrating a possible embodiment of a domainname control based social website account authentication method.

FIG. 8 is a flow diagram illustrating a possible embodiment of a publickey certificate based social website account authentication method.

FIG. 9 is a flow diagram illustrating a possible embodiment of a publickey certificate based social website account authentication method.

FIG. 10 is a flow diagram illustrating a possible embodiment of a publickey certificate based social website account authentication method.

FIG. 11 is a flow diagram illustrating a possible embodiment of abusiness validation based social website account authentication method.

FIG. 12 is a flow diagram illustrating a possible embodiment of abusiness validation based social website account authentication method.

FIG. 13 is a flow diagram illustrating a possible embodiment of abusiness validation based social website account authentication method.

FIG. 14 is an illustration of a system that may be used for socialwebsite account authentication.

DETAILED DESCRIPTION

The present inventions will now be discussed in detail with regard tothe attached drawing figures which were briefly described above. In thefollowing description, numerous specific details are set forthillustrating the Applicant's best mode for practicing the inventions andenabling one of ordinary skill in the art to make and use theinventions. It will be obvious, however, to one skilled in the art thatthe present inventions may be practiced without many of these specificdetails. In other instances, well-known machines, structures, and methodsteps have not been described in particular detail in order to avoidunnecessarily obscuring the present inventions. Unless otherwiseindicated, like parts and method steps are referred to with likereference numerals.

A network is a collection of links and nodes (e.g., multiple computersand/or other devices connected together) arranged so that informationmay be passed from one part of the network to another over multiplelinks and through various nodes. Examples of networks include theInternet, the public switched telephone network, the global Telexnetwork, computer networks (e.g., an intranet, an extranet, a local-areanetwork, or a wide-area network), wired networks, and wireless networks.

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweencomputer users. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information (e.g.,text, graphics, audio, video, animation, and other forms of data) atspecific locations on the Internet referred to as webpages. Websitescomprise a collection of connected, or otherwise related, webpages. Thecombination of all the websites and their corresponding webpages on theInternet is generally known as the World Wide Web (WWW) or simply theWeb.

For Internet users and businesses alike, the Internet continues to beincreasingly valuable. More people use the Web for everyday tasks, fromsocial networking, shopping, banking, and paying bills to consumingmedia and entertainment. E-commerce is growing, with businessesdelivering more services and content across the Internet, communicatingand collaborating online, and inventing new ways to connect with eachother.

Prevalent on the Web are multimedia websites, some of which may offerand sell goods and services to individuals and organizations. Websitesmay consist of a single webpage, but typically consist of multipleinterconnected and related webpages. Websites, unless extremely largeand complex or have unusual traffic demands, typically reside on asingle server and are prepared and maintained by a single individual orentity. Menus and links may be used to move between different webpageswithin the website or to move to a different website as is known in theart. The interconnectivity of webpages enabled by the Internet can makeit difficult for Internet users to tell where one website ends andanother begins.

Websites may be created using HyperText Markup Language (HTML) togenerate a standard set of tags that define how the webpages for thewebsite are to be displayed. Users of the Internet may access contentproviders' websites using software known as an Internet browser, such asMICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX. After the browser haslocated the desired webpage, it requests and receives information fromthe webpage, typically in the form of an HTML document, and thendisplays the webpage content for the user. The user then may view otherwebpages at the same website or move to an entirely different websiteusing the browser.

Some Internet users, typically those that are larger and moresophisticated, may provide their own hardware, software, and connectionsto the Internet. But many Internet users either do not have theresources available or do not want to create and maintain theinfrastructure necessary to host their own websites. To assist suchindividuals (or entities), hosting companies exist that offer websitehosting services. These hosting providers typically provide thehardware, software, and electronic communication means necessary toconnect multiple websites to the Internet. A single hosting provider mayliterally host thousands of websites on one or more hosting servers.

Browsers are able to locate specific websites because each website,resource, and computer on the Internet has a unique Internet Protocol(IP) address. Presently, there are two standards for IP addresses. Theolder IP address standard, often called IP Version 4 (IPv4), is a 32-bitbinary number, which is typically shown in dotted decimal notation,where four 8-bit bytes are separated by a dot from each other (e.g.,64.202.167.32). The notation is used to improve human readability. Thenewer IP address standard, often called IP Version 6 (IPv6) or NextGeneration Internet Protocol (IPng), is a 128-bit binary number. Thestandard human readable notation for IPv6 addresses presents the addressas eight 16-bit hexadecimal words, each separated by a colon (e.g.,2EDC:BA98:0332:0000:CF8A:000C:2154:7313).

IP addresses, however, even in human readable notation, are difficultfor people to remember and use. A Uniform Resource Locator (URL) is mucheasier to remember and may be used to point to any computer, directory,or file on the Internet. A browser is able to access a website on theInternet through the use of a URL. The URL may include a HypertextTransfer Protocol (HTTP) request combined with the website's Internetaddress, also known as the website's domain name. An example of a URLwith a HTTP request and domain name is: http://www.companyname.com. Inthis example, the “http” identifies the URL as a HTTP request and the“companyname.com” is the domain name.

Domain names are much easier to remember and use than theircorresponding IP addresses. The Internet Corporation for Assigned Namesand Numbers (ICANN) approves some Generic Top-Level Domains (gTLD) anddelegates the responsibility to a particular organization (a “registry”)for maintaining an authoritative source for the registered domain nameswithin a TLD and their corresponding IP addresses. For certain TLDs(e.g., .biz, .info, .name, and .org) the registry is also theauthoritative source for contact information related to the domain nameand is referred to as a “thick” registry. For other TLDs (e.g., .com and.net) only the domain name, registrar identification, and name serverinformation is stored within the registry, and a registrar is theauthoritative source for the contact information related to the domainname. Such registries are referred to as “thin” registries. Most gTLDsare organized through a central domain name Shared Registration System(SRS) based on their TLD.

The process for registering a domain name with.com, .net, .org, and someother TLDs allows an Internet user to use an ICANN-accredited registrarto register their domain name. For example, if an Internet user, JohnDoe, wishes to register the domain name “mycompany.com,” John Doe mayinitially determine whether the desired domain name is available bycontacting a domain name registrar. The Internet user may make thiscontact using the registrar's webpage and typing the desired domain nameinto a field on the registrar's webpage created for this purpose. Uponreceiving the request from the Internet user, the registrar mayascertain whether “mycompany.com” has already been registered bychecking the SRS database associated with the TLD of the domain name.The results of the search then may be displayed on the webpage tothereby notify the Internet user of the availability of the domain name.If the domain name is available, the Internet user may proceed with theregistration process. If the domain name is not available forregistration, the Internet user may keep selecting alternative domainnames until an available domain name is found.

Social websites may comprise Internet-based social networking servicesthat focus on building online social networks for communities of peoplewho may share interests and activities, wish to communicate with eachother efficiently, and may be interested in exploring the interests andactivities of others, and which necessitates the use of softwareapplications. Most social websites are Internet based and provide acollection of various ways for users to interact, such asmicro-blogging, blogging, chat, forums, instant messaging, email, video,voice chat, file sharing, discussion groups, etc. The main types ofsocial networking services are those that contain directories of somecategories (such as former classmates), means to connect and communicatewith friends, and/or recommendation systems linked to trust. Popularsocial websites now combine many of these, with TWITTER, MYSPACE,FACEBOOK, YOUTUBE, LINKEDIN, and FLICKR being but a few examples.

Many social websites require their users to generate social websiteaccounts to use the website. Among other purposes, the account may allowthe social website to identify the user to other users online. Theaccount generation process may include providing a variety ofinformation that may be used to identify the user on the social websiteand/or generate a login/password combination for user authenticationpurposes. The information typically may be collected during a first-useregistration process and may comprise requesting a broad array ofinformation, perhaps ranging from no information to an email address toname, address, email address, and/or more specific information.

Generally, there is little or no verification of such user-providedinformation performed by the social website. Thus, an anonymous user mayregister as a famous person (or agent of a business or otherorganization) and participate on the social website as the famous person(or on behalf of the business or other organization). Applicant hastherefore determined that presently-existing methods do not provideadequate means for verifying the authenticity of social websiteaccounts. For these reasons, there is a need for the methods forauthenticating social website accounts (and related functionality) asdescribed herein.

Domain Name Control Based Social Website Account Authentication Methods

FIG. 1 illustrates a domain name control based social website accountauthentication method that may comprise the steps of receiving a requestto verify the authenticity of a social website account (the request mayinclude account registration information such as a business name and abusiness email address comprising a domain name) (Step 100) anddetermining whether the domain name is registered to (and/or undercontrol of) the business (Step 110). If so, the authenticity of thesocial website account may be certified (Step 120).

A request to verify the authenticity of a social website account may bereceived (Step 100) from any individual or entity that may provide anaccount-based social website. A social website may comprise any softwareapplication that may focus on building and verifying online socialnetworks for communities of people who may share interests andactivities, wish to communicate with each other efficiently, and may beinterested in exploring the interests and activities of others, andwhich necessitates the use of software applications. TWITTER, FACEBOOK,MYSPACE, and LINKEDIN are a few well-known examples of social websites.

The software application may comprise any client-side, server-side, orother software application that utilizes screen names to identify users.As non-limiting examples, the software application may comprise a blogapplication, micro-blogging application, chat application, forumapplication, social networking website application, instant messagingapplication and/or any combination thereof.

A blog (i.e., weblog) application may comprise a hosted website, perhapsmaintained by an individual with regular entries of written commentary,or other material such as graphics or video, perhaps related to aparticular topic. The ability for blog readers to comment on blogentries in an interactive format is common functionality implementedwith many blogs. Both the blogger and readers may be identified in thecommentary section by screen names that may be selected and registered,perhaps with the blog application.

A micro-blogging application may comprise a particular type of bloggingapplication that allows users to send brief text (or perhapssmall-file-size multimedia) updates to a website to be viewed byInternet users. The content of a micro-blog differs from a traditionalblog in that it is typically smaller in actual size and aggregate filesize. Such micro-blogs may be submitted by varying means, includingwebsite text entry or multimedia file uploads, text messaging, instantmessaging, and/or email. As with blogs, micro-bloggers may subscribe toa micro-blogging service (e.g., TWITTER) that may require participantsto register a screen name to participate. TWITTER for example, allowsusers to register screen names called “Twitter Handles” in the followingformat: @screenname. Continuing with the example from above, John Doe(who works at My Company) may register the screen name (i.e., TwitterHandle) “@johndoe,” while official company micro-blogs may be postedunder the screen name “@mycompany.”

An instant messaging application may comprise an instant messagingsoftware application that allows one user to communicate with anotherover a network in real time. The instant messaging software applicationmay comprise proprietary or third-party (e.g., MICROSOFT OFFICECOMMUNICATOR, JABBER, GTALK, SKYPE, MEEBO, ICQ, YAHOO! MESSENGER, MSNMESSENGER, PIDGIN, and/or AOL INSTANT MESSENGER) systems. Many instantmessaging software applications allow users to register a screen nameand subsequently generate a contact list by adding other user's screennames to the list. If a user is online, their screen name may bedisplayed indicating that user may be available for instant messaging.Clicking on a user's name may activate an instant messaging window inwhich messages may be typed and responses received. User comments aregenerally identified by the user's screen name.

A chat application may comprise an electronic discussion group softwareapplication (i.e., text chat) that allows users to join chat rooms andpublicly communicate with many users at the same time. Example chatprotocols that may be utilized include, as non-limiting examples,Internet Relay Chat (IRC) and/or eXtensible Messaging and PresenceProtocol (XMPP). In many discussion group applications, users may join apre-existing chat room or create a chat room about any topic. Once inthe chat room, users may type messages that other users in the room canread, as well as respond to messages from others. Such Chat applicationsgenerally require users to register a screen name to participate. Usercomments are generally identified by the user's screen name.

A forum application may comprise an online group discussion websiteapplication for displaying and managing user-generated content, perhapsrelating to a particular topic (or topics). The forum application mayallow users to post comments (perhaps in text or multimedia format)regarding the topic(s) and may require Internet users to become members(i.e., register with the application) before being allowed to submitmessages (“posts”). The registration process typically comprises ageverification and agreement to the forum application's terms of service.Registered members may be assigned (or select) a screen name that may bedisplayed with the user's submitted post. Forum applications may beavailable for implementation on a website via the Internet and may bewritten in a variety of programming languages, such as PHP, Perl, Java,and/or ASP.

The term “social website account” is meant to be broadly construed toinclude any established relationship between a user and a website,computer, network, and/or other information service. Social websites mayuse such social website accounts to identify a user, perhaps by a screenname, which may comprise an alphanumeric, ASCII, or other sequence ofcharacters, images, and/or file types used by a software application toidentify a user to other users, such as on a social website. To log into a social website account, the user may be required to authenticatehimself with a password (possible his screen name) or other credentialsfor the purposes of accounting, security, logging, and resourcemanagement.

The request to verify a social website account may comprise anycommunication seeking verification of a social website account'sauthentication including, but not limited to, an electronic requestreceived by the server computer including, but not limited to, a HyperText Transfer Protocol (HTTP) request, email message, Short MessageService (SMS) message (i.e., text message), and/or function call on anApplications Programming Interface (API). The request may include anyinformation about the social website account that may be useful to theprocess of verifying the account's authenticity.

As a non-limiting example, the request may include information receivedfrom a user by the social website during a registration or accountgeneration process. Such information may include the user's name,address, phone number, domain name, and/or email address. If the user isa business or business employee, the information may include thebusiness name, business email address, business phone number, businessdomain name, and/or employee names. Alternatively, the request maycomprise information that was not provided by the user. As anon-limiting example, such information may comprise information aboutthe user obtained by or in the possession of the social website fromother sources, such as publically-available information.

The illustrated embodiments place no limitation on the format the domainname may take. While future iterations of the DNS may establishalternate domain name formats (perhaps using different alphanumericstructures or file types such as image, audio, or video filesfunctioning as a domain name or a similarly-functioning resourcelocator), which are explicitly contemplated by this patent application,the traditional domain name structure comprises a root name (i.e.,“mycompany” in the domain name mycompany.com) concatenated to atop-level domain (i.e., “.com” in the domain name mycompany.com). Inthis construct, an email address may comprise a username concatenated toa domain name (e.g., user@mycompany.com). Software and/or scripts,perhaps running on the at least one server, may parse the domain namefrom any provided email to perform subsequent steps.

Whether the domain name is registered to and/or under control of theprovided business name then may be determined (Step 110). This step maybe accomplished by any method of verifying domain name registrationand/or control known in the art or developed in the future. As anon-limiting example (and as illustrated in FIG. 2), Step 110 may beaccomplished by analyzing a WHOIS data for the domain name (Step 200),identifying an administrative contact from the WHOIS data (Step 210),contacting the administrative contact (Step 220), and receiving aresponse from the administrative contact confirming that the domain nameis registered to and under control of the business (Step 230).

The WHOIS system is a TCP-based (Transmission Control Protocol)transaction-oriented query/response protocol and system that is used toprovide information services to Internet users. It is widely used forquerying databases in order to determine the registrant, administrativecontact, technical contact, or other information regarding a domainname. While originally used to provide “white pages” services andinformation about registered domain names, current deployments cover amuch broader range of information services. The protocol delivers itscontent (WHOIS data) in a human-readable format. WHOIS data may beobtained by transmitting a request to a WHOIS server listening on a TCPport for requests from WHOIS clients. The WHOIS client may make a textrequest to the WHOIS server, which may reply in kind with text content.The WHOIS server may close its connection as soon as the output isfinished. The closed TCP connection is the indication to the client thatthe response has been received. Once received, the domain name's WHOISdata may be analyzed (Step 200) and the administrative contact for thedomain name may be identified (Step 210).

The domain name's administrative contact may then be contacted (Step220) to ascertain whether the domain name is registered to and/or undercontrol of the subject business. The administrative contact may becommunicated with via any method or means of communication known in theart or developed in the future including, but not limited to direct,person-to-person, written, telephonic, and/or electronic communicationsmeans. As a non-limiting example, where the WHOIS data comprises anadministrative contact email address, the administrative contact may becontacted by sending an email message, perhaps containing a hyperlinkthat, when received and clicked, may transmit a response, which willindicate email account control. Thus, as illustrated in FIG. 3, the stepof contacting the domain name's administrative contact (Step 220) may beaccomplished by sending an email message, perhaps containing ahyperlink, to the administrative contact's email address (Step 300) andreceiving an HTTP request that may originate from the hyperlink (Step310).

Alternatively, and as illustrated in FIG. 4, domain name registrationand/or control may be determined (Step 110) by sending an email message(or other communication as described above) to the business emailaddress provided in the original request, wherein the email messagecomprises at least one instruction for verifying that the domain name isregistered to and under control of said business name (Step 400). Theemail message may comprise any instruction or instructions that, ifcomplied with, demonstrate domain name registration and/or control.

As a non-limiting example, the email message (or other communication asdescribed above) may comprise at least one instruction to modify a CNAMErecord for the domain name. A CNAME record is a type of resource recordin the DNS system that specifies whether the domain name is an alias ofanother domain name. Only an individual or entity having control overthe domain name may modify the CNAME record. By determining whether theCNAME record was modified according to the email's instructions (perhapsby analyzing the domain name's DNS record), domain name registrationand/or control may be determined (Step 110).

As another non-limiting example, the email message (or othercommunication as described above) may comprise at least one instructionto upload an HTML file (and/or any other file type that may be uploadedto—and detected on—a webpage) to a webpage resolving from the domainname. The email message may contain the HTML file itself, a hyperlink tothe HTML file, or simply a file name for an HTML file. Once the HTMLfile has been uploaded, an Internet user may detect the file on thewebpage (perhaps by accessing the webpage via a browser). If the file isdetected, domain name registration and/or control has been demonstrated(Step 110).

Returning to FIG. 1, the illustrated process may conclude by (responsiveto a determination that the domain name is registered to and undercontrol of the business) certifying the authenticity of the socialwebsite account (Step 120). This step may be accomplished by any methodknown in the art or developed in the future of informing the socialwebsite that the social website account is authentic. As a non-limitingexample, the certification (Step 120) may be accomplished by notifyingthe social website that the domain name is registered to and undercontrol of the business. Such notification may be communicated via anymethod or means of communication known in the art or developed in thefuture including, but not limited to any electronic response received(perhaps at a server computer responsive to a request sent in kind)including, but not limited to, a Hyper Text Transfer Protocol (HTTP)request, email message, and/or Short Message Service (SMS) message(i.e., text message). Notification also may be received via paper mail,telephone conversation, person to person contact, or any other means forreceiving screen name availability notice known in the art or developedin the future.

As a non-limiting example, such notification may be accomplished bytransmitting a certification seal to the social website. Thecertification seal may indicate to social website users that the socialwebsite account they may be accessing has been validated. It may be inthe form of a displayable image, perhaps a digital certificate fordisplay on a webpage. The certification seal also may take the form of achange in appearance of the social website (or the URL bar in a browser)when it appears on a computer screen. It also could comprise an audiblesound, such as an audio file that plays when the social website accountis accessed (e.g., chimes).

Methods for providing a certification seal to a social website include,but are not limited to: (1) sending a piece of software to the socialwebsite (or other individual or entity) for installation on a hostingcomputer, server, website, database, or other storage device; (2)storing the certification seal on a computer, server, website, database,or other storage device from which the social website may retrieve thecertification seal; or (3) sending the certification seal to a thirdparty for storage on a computer, server, website, database, or otherstorage device from which the social website (or other individual orentity) may retrieve the certification seal.

Alternatively, the social website may be notified that the domain nameis registered to and under control of the business by validating saidsocial website account via the social website's Applications ProgrammingInterface (API). An API is a software-to-software interface thatspecifies the protocol defining how independent computer programsinteract or communicate with each other. The API may allow a requestingparty's software to communicate and interact with the softwareapplication and/or its provider—perhaps over the network—through aseries of function calls (requests for services). It may comprise aninterface provided by the social website and/or its provider to supportfunction calls made of the social website by other computer programs,perhaps those utilized by the requesting party to determine screen nameavailability. The API may comprise any API type known in the art ordeveloped in the future including, but not limited to, request-style,Berkeley Sockets, Transport Layer Interface (TLI), RepresentationalState Transfer (REST), SOAP, Remote Procedure Calls (RPC), StandardQuery Language (SQL), file transfer, message delivery, and/or anycombination thereof.

FIG. 5 illustrates another embodiment of a domain name control basedsocial website account authentication method. The illustrated method maycomprise the step of sending (perhaps by at least one server computercommunicatively coupled to a network) a request to verify theauthenticity of a social website account (the request may includeaccount registration information such as a business name and a businessemail address comprising a domain name) (Step 500). The request may comefrom any individual or entity offering, hosting, or otherwise providinga social website that utilizes social website accounts, which may needauthenticity verification. The request may comprise any electronicrequest received by a server computer including, but not limited to, aHyper Text Transfer Protocol (HTTP) request, email message, and/or ShortMessage Service (SMS) message (i.e., text message). The request maycomprise any combination of data seeking to verify the authenticity of asocial website account.

As a non-limiting example, the request may include information receivedfrom a user by the social website during a registration or accountgeneration process. Such information may include the user's name,address, phone number, domain name, and/or email address. If the user isa business or business employee, the information may include thebusiness name, business email address, business phone number, businessdomain name, and/or employee names. Alternatively, the request maycomprise information that was not provided by the user. As anon-limiting example, such information may comprise information aboutthe user obtained by or in the possession of the social website fromother sources, such as publically-available information.

Subsequent to transmitting the request (Step 500), confirmation that thedomain name is registered to and under control of the business nameprovided in the request may be received (Step 510). As a non-limitingexample, and as illustrated in FIGS. 6-7, the received confirmation maybe obtained by any of the methods for determining domain nameregistration and control described above with respect to Steps 110,200-230, 300, 310, 400, and 410. The illustrated process may conclude bycertifying the authenticity of the social website account as describedin detail above with respect to Step 120.

Public Key Certificate Based Social Website Account AuthenticationMethods

FIG. 8 illustrates a public key certificate based social website accountauthentication method that may comprise the step of receiving a requestto verify the authenticity of a social website account (the request mayinclude account registration information such as a business name and abusiness email address comprising a domain name) (Step 100). Whether apublic key certificate has been issued for the domain name may then bedetermined (Step 800). A public key certificate is an electronicdocument that may use a digital signature to bind together a public keywith an entity (e.g., an individual, business, governmental entity,etc.). The certificate may be used to verify that a public key belongsto that entity. When issued to a website resolving from a domain name,it may serve to verify that the domain name is under that entity'scontrol.

As a non-limiting example, the public key certificate may comprise anydigital certificate using the public key infrastructure, such as aSecure Sockets Layer (SSL) or Transport Layer Security (TLS)certificate. SSL includes a protocol for transmitting private documentsvia the Internet by using a private key to encrypt data transferred overan SSL connection. An SSL certificate lets users know that the websiteowner/operator has been verified by a trusted third party (a CertificateAuthority) and that confidential communications with the website areencrypted. The SSL certificate typically includes an identification ofthe server (such as its hostname), the server's public key, a digitalsignature provided by the Certificate Authority, the subject domainname, and the individual or business to which the certificate has beenissued. Common conventional browsers, such as INTERNET EXPLORER orMOZILLA FIREFOX, support the SSL protocol, and many websites use theprotocol to obtain confidential user information from their Customers.By convention, Uniform Resource Locators (URLs) that require an SSLconnection start with “https:” instead of “http:.”

Step 800 (determining whether a public key certificate has been issuedfor the domain name) may be accomplished by, as a non-limiting example,directly querying the hosting provider hosting the social websiteresolving from the domain name to determine whether an SSL certificatehas been issued for the domain name. Alternatively, the domain name maybe entered in a browser address bar subsequent to “https://.” If thedomain name resolves to a website, it has been issued an SSLcertificate. If an SSL certificate has been issued, the certificate maybe analyzed to determine whether it identifies the business namereceived in Step 100 (Step 810). This step may be accomplished byparsing the SSL certificate into data fields and extracting the businessname and/or other relevant information, such as the domain name. If theSSL certificate properly identifies both the business name and thedomain name, the relationship between the business name and domain namemay thereby be positively established.

The illustrated method may further comprise the step of determiningwhether the business email address is under the control of the business(Step 820). As illustrated in FIG. 9, this step may be accomplished (asa non-limiting example) by sending an email message, perhaps containinga hyperlink, to the business email address (Step 900) and receiving anHTTP request that may originate from the hyperlink (Step 900). If aresponse is received, control of the email account by the business isestablished. The authenticity of the social website account may then becertified (Step 120) as described in detail above.

FIG. 10 illustrates another embodiment of a public key certificate basedsocial website account authentication method that may comprise the stepof sending (perhaps by at least one server computer communicativelycoupled to a network) a request to verify the authenticity of a socialwebsite account (the request may include account registrationinformation such as a business name and a business email addresscomprising a domain name) (Step 500). In response to the request,confirmation may be received that: (1) the domain name and/or businessname are listed in a public key certificate issued for the domain name;and (2) the email address is under the control of the business namereceived in the request (Step 1000). The confirmations may be obtainedvia any of the methods discussed in detail above with regard to FIGS. 8and 9. The authenticity of the social website account may then becertified (Step 120) as described in detail above.

Business Validation Based Social Website Account Authentication Methods

FIG. 11 illustrates a business validation based social website accountauthentication method that may comprise the step of receiving a requestto verify the authenticity of a social website account (the request mayinclude account registration information such as a business name and abusiness email address comprising a domain name) (Step 100). Thevalidation request received in Step 100 may further comprise anyadditional information regarding the business and/or the individual thatestablished the social website account including, but not limited to,employee name, a business address, and/or a business telephone number.

Following receipt of such a request, the social website account may bevalidated by validating the business (Step 1110), validating thebusiness email address (Step 820), and determining whether the domainname is registered to and under control of the business (Step 110).These steps may be performed either in series or in parallel. Responsiveto a determination that the business name and business email address arevalidated and that the domain name is registered to and under control ofthe business name, the authenticity of the social website account may becertified (Step 120). This method may provide a high-assurance guarantythat the social website account is authentic by combining thepreviously-described steps with a business validation element.

The business may be validated (Step 100) by any method known in the artor developed in the future of confirming that the business name providedin the request (Step 100) is a legal, existing business. As anon-limiting example, public business records (e.g., state corporationcommission records, federal SEC records, business directories, and/oronline phonebooks) may be searched to identify the business name.Alternatively, private databases (e.g., ZOOMINFO) may be accessed andsearched. A positive result (i.e., an exact match of the providedbusiness name in the directory) validates the business' existence. Asshown in FIG. 12, business email address validation (Step 820),determination of domain name registration and/or control (Step 110), andsocial website account certification (Step 120) may be accomplished asdescribed in detail above.

In the alternate embodiment illustrated in FIG. 13, responsive to adetermination that the business name and/or business email address isnot validated, or that the domain name is not registered to and undercontrol of the business name, a manual business verification process maybe performed. The manual verification process may comprise an individualsearching (perhaps via a computer communicatively coupled to a network)public and/or private business records. It also may comprise calling aprovided business telephone number to verify that the phone number is infact related to the business and/or whether the employee who establishedthe social website account is in fact employed by the business and/orauthorized to establish a social website account on its behalf.Responsive to a positive result from said manual validation process,certifying, by said at least one server computer, the authenticity ofthe social website account may be certified (Step 120).

FIG. 14 is an illustration of a system that may be used for socialwebsite account authentication. As a non-limiting example, the methodillustrated in FIG. 1 (and all steps of all methods described herein)may be performed by any central processing unit (CPU) in any computingsystem, such as a microprocessor running on at least one server, andexecuting instructions stored (perhaps as scripts and/or software) incomputer-readable media accessible to the CPU, such as a hard disk driveon a server. The server(s) may be communicatively coupled to a network(such as the Internet) and at least one client that, collectively (alongwith the software described herein), may allow social website accountauthentication.

Such servers could comprise any computer or program that providesservices to other computers, programs, or users either in the samecomputer or over a computer network. As non-limiting examples, serversmay comprise application, communication, mail, database, proxy, fax,file, media, web, peer-to-peer, standalone, software, or hardwareservers (i.e., server computers) and may use any server format known inthe art or developed in the future (possibly a shared hosting server, avirtual dedicated hosting server, a dedicated hosting server, a cloudhosting solution, a grid hosting solution, or any combination thereof).Clients that may be used to connect to the network to use theillustrated embodiments may include a desktop computer, a laptopcomputer, a hand held computer, a terminal, a television, a televisionset top box, a cellular phone, a wireless phone, a wireless hand helddevice, an Internet access device, a rich client, thin client, or anyother client functional with a client/server computing architecture.

The example embodiments herein place no limitation on networkconfiguration or connectivity. Thus, as non-limiting examples, thenetwork could comprise the Internet, the public switched telephonenetwork, the global Telex network, computer networks (e.g., an intranet,an extranet, a local-area network, or a wide-area network), wirednetworks, wireless networks, or any combination thereof. Examples ofclients that may be used may include a desktop computer, a laptopcomputer, a hand held computer, a terminal, a television, a televisionset top box, a cellular phone, a wireless phone, a wireless hand helddevice, an Internet access device, a rich client, thin client, or anyother client functional with a client/server computing architecture.

Servers and clients may be communicatively coupled to the network viaany method of network connection known in the art or developed in thefuture including, but not limited to wired, wireless, modem, dial-up,satellite, cable modem, Digital Subscriber Line (DSL), AsymmetricDigital Subscribers Line (ASDL), Virtual Private Network (VPN),Integrated Services Digital Network (ISDN), X.25, Ethernet, token ring,Fiber Distributed Data Interface (FDDI), IP over Asynchronous TransferMode (ATM), Infrared Data Association (IrDA), wireless, WAN technologies(T1, Frame Relay), Point-to-Point Protocol over Ethernet (PPPoE), and/orany combination thereof.

Other embodiments and uses of the above inventions will be apparent tothose having ordinary skill in the art upon consideration of thespecification and practice of the inventions disclosed herein. Thespecification and examples given should be considered exemplary only,and it is contemplated that the appended claims will cover any othersuch embodiments or modifications as fall within the true scope of theinventions.

The Abstract accompanying this specification is provided to enable theUnited States Patent and Trademark Office and the public generally todetermine quickly from a cursory inspection the nature and gist of thetechnical disclosure and in no way intended for defining, determining,or limiting any of its embodiments.

The inventions claimed are:
 1. A method comprising the steps of: A)receiving, by at least one server computer communicatively coupled to anetwork, a request to verify the authenticity of a social websiteaccount, said request comprising a business name and a business emailaddress comprising a domain name; B) determining, by said at least oneserver computer, whether said domain name is registered to and undercontrol of said business name; and C) responsive to a determination thatsaid domain name is registered to and under control of said businessname, certifying, by said at least one server computer, the authenticityof said social website account.
 2. The method of claim 1, wherein saidsocial website comprises a micro-blogging website.
 3. The method ofclaim 1, wherein said social website comprises a software applicationselected from the group consisting of a micro-blogging application, achat application, a forum application, a social networking application,a blog application, and an instant messaging application.
 4. The methodof claim 3, wherein said software application comprises a server-sidesoftware application.
 5. The method of claim 3, wherein said softwareapplication comprises a client-side software application.
 6. The methodof claim 1, wherein said determining step B) comprises the steps of: i)analyzing a WHOIS data for said domain name; ii) identifying anadministrative contact from said WHOIS data; iii) contacting saidadministrative contact; and iv) receiving confirmation from saidadministrative contact confirming that said domain name is registered toand under control of said business name.
 7. The method of claim 6,wherein said WHOIS data comprises an administrative contact emailaddress.
 8. The method of claim 7, wherein said contacting step iii)comprises sending an email message to said administrative contact emailaddress.
 9. The method of claim 8, wherein said administrative contactemail message comprises a hyperlink.
 10. The method of claim 9, whereinsaid receiving step iii) comprises receiving an HTTP request originatingfrom said hyperlink.
 11. The method of claim 1, wherein said determiningstep B) comprises sending an email message to said business emailaddress, said email message comprising at least one instruction forverifying that said domain name is registered to and under control ofsaid business name.
 12. The method of claim 11, wherein said emailmessage comprises at least one instruction to modify a CNAME record forsaid domain name.
 13. The method of claim 12, wherein said determiningstep B) further comprises determining that said CNAME record wasmodified according to said at least one instruction by analyzing a DNSrecord for said domain name.
 14. The method of claim 11, wherein saidemail message comprises at least one instruction to upload an HTML fileto a webpage resolving from said domain name.
 15. The method of claim14, wherein said email message further comprises said HTML file.
 16. Themethod of claim 14, wherein said email message further comprises a filename for said HTML file.
 17. The method of claim 14, wherein saiddetermining step B) further comprises determining that said HTML filehas been uploaded to said webpage.
 18. The method of claim 1, whereinsaid certifying step C) comprises notifying said social website thatsaid domain name is registered to and under control of said businessname.
 19. The method of claim 1, wherein said certifying step C)comprises transmitting a certification seal to said social website. 20.The method of claim 1, wherein said certifying step C) comprisesvalidating said social website account via said social website'sapplication programming interface.
 21. A method comprising the steps of:A) sending, by at least one server computer communicatively coupled to anetwork, a request to verify the authenticity of a social websiteaccount, said request comprising a business name and a business emailaddress comprising a domain name; B) receiving, by said at least oneserver computer, confirmation that said domain name is registered to andunder control of said business name; and C) certifying, by said at leastone server computer, the authenticity of said social website account.22. The method of claim 21, wherein said social website comprises amicro-blogging website.
 23. The method of claim 21, wherein said socialwebsite comprises a software application selected from the groupconsisting of a micro-blogging application, a chat application, a forumapplication, a social networking application, a blog application, and aninstant messaging application.
 24. The method of claim 23, wherein saidsoftware application comprises a server-side software application. 25.The method of claim 20, wherein said confirmation is obtained by: i)analyzing a WHOIS data for said domain name; ii) identifying anadministrative contact from said WHOIS data; iii) contacting saidadministrative contact; and iv) receiving confirmation from saidadministrative contact that said domain name is registered to and undercontrol of said business name.
 26. The method of claim 25, wherein saidWHOIS data comprises an administrative contact email address.
 27. Themethod of claim 25, wherein said contacting step iii) comprises sendingan email message to said administrative contact email address.
 28. Themethod of claim 27, wherein said administrative contact email messagecomprises a hyperlink.
 29. The method of claim 28, wherein saidreceiving step iii) comprises receiving an HTTP request originating fromsaid hyperlink.
 30. The method of claim 20, wherein said confirmation isobtained by sending an email message to said business email address,said email message comprising at least one instruction for verifyingthat said domain name is registered to and under control of saidbusiness name.
 31. The method of claim 30, wherein said email messagecomprises at least one instruction to modify a CNAME record for saiddomain name.
 32. The method of claim 31, wherein said confirmation isobtained by determining that said CNAME record was modified according tosaid at least one instruction by analyzing a DNS record for said domainname.
 33. The method of claim 30, wherein said email message comprisesat least one instruction to upload an HTML file to a webpage resolvingfrom said domain name.
 34. The method of claim 33, wherein said emailmessage further comprises said HTML file.
 35. The method of claim 33,wherein said email message further comprises a file name for said HTMLfile.
 36. The method of claim 14, wherein said confirmation is obtainedby determining that said HTML file has been uploaded to said webpage.37. The method of claim 21, wherein said certifying step C) comprisesdisplaying an indicia of certification on said social website.